Claude (Anthropic) End of Life (EOL) Dates & Support Timeline

Claude (Anthropic) lifecycle status — the real story

Anthropic publishes a four-stage lifecycle for Claude models: Active (fully supported and recommended), Legacy (no further updates, may be deprecated), Deprecated (still functional, not recommended, with a named replacement and a retirement date), and Retired (requests fail). Customers with active deployments get at least 60 days' notice before a publicly released model is retired, and the published table gives each active model a 'not sooner than' retirement floor.

The dates apply to Anthropic-operated platforms; Amazon Bedrock and Google Cloud set their own retirement schedules, so the same model can have a different status there. The end-of-life dates above are the published retirement dates and floors.

Verified against the vendor's lifecycle documentation on August 22, 2026.

Claude (Anthropic) release and support pattern

Of the 32 release lines tracked, 19 are past end of life and 13 are still within support. The newest line, claude-mythos-5-1, was released September 1, 2026. The next scheduled end of life is claude-sonnet-4-5-20250929 on September 29, 2026 — 27 days from this build. The longest-supported line currently published is claude-fable-5-1, to September 1, 2027.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

What does Claude (Anthropic) end of life mean for your organization?

When a version of Claude (Anthropic) reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL Claude (Anthropic) should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when Claude (Anthropic) reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Related Products